[v4.5] libpod: use new libcontainer BlockIO constructors#19136
[v4.5] libpod: use new libcontainer BlockIO constructors#19136openshift-merge-robot merged 1 commit intocontainers:v4.5from
Conversation
|
PTAL @vrothberg @mheon @Luap99 @lsm5 |
|
LGTM |
|
@haircommander remind me why the cherrypick to this branch. Is it for rhel ? |
|
we can ignore packit failures for now, and maybe only do centos builds for rhel branches |
|
hit the wrong button, my bad. |
|
CRI-O will eventually vendor this commit, no need for a packaged version or even a tag. |
[NO NEW TESTS NEEDED] Signed-off-by: Peter Hunt <pehunt@redhat.com>
haircommander
force-pushed
the
bump-runc-4.5
branch
from
e1ef65d to
9f90a86
Compare
|
/lgtm |
openshift-ci
bot
added
the
do-not-merge/hold
|
/approve |
openshift-ci
bot
removed
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@saschagrunert: new pull request could not be created: failed to create pull request against containers/podman#v4.6 from head openshift-cherrypick-robot:cherry-pick-19136-to-v4.6: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between containers:v4.6 and openshift-cherrypick-robot:cherry-pick-19136-to-v4.6"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
They're already in both branches. We should only backport after things are in main. |
|
Found the issue: v4.6.0-rc1 does not have the change in yet, so we wait for another RC or the final version. :) |
|
rc2 should be going out today |
github-actions
bot
added
the
locked - please file new issue/PR
8 participants
[NO NEW TESTS NEEDED]
Does this PR introduce a user-facing change?